Modifying a Circuit Design

ABSTRACT

Embodiments describing an approach to detecting negative paths for a circuit design based on a circuit timing test of the circuit design. Assigning each negative path to a logic bucket, an integration bucket, or a macro bucket, wherein the logic bucket corresponds to logic design flaws, the integration bucket corresponds to integration design flaws, and the macro bucket corresponds to macro design flaws or design flaws residing within a macro of the circuit design. Detecting a modification to the circuit design based on the logic design flaws, the integration design flaws, and the macro design flaws, and applying the modification to the circuit design to enable manufacturing an integrated circuit, wherein an overall delay between two latches of the integrated circuit is below a predetermined threshold.

BACKGROUND OF THE INVENTION

The present disclosure relates to circuit designs, and morespecifically, but not exclusively, to modifying a circuit design basedon a type of design flaw.

SUMMARY

According to an embodiment, a method for modifying circuits can includedetecting, by one or more processors, negative paths for a circuitdesign based on a circuit timing test of the circuit design. The methodcan also include assigning, by the one or more processors, each negativepath to a logic bucket, an integration bucket, and/or a macro bucket,wherein the logic bucket corresponds to logic design flaws, theintegration bucket corresponds to integration design flaws, and themacro bucket corresponds to macro design flaws or design flaws residingwithin a macro of the circuit design. Further, the method can includedetecting, by one or more processors, a priority of the logic designflaws, the integration design flaws, and the macro design flaws; andassigning each negative path to the logic bucket, the integrationbucket, and the macro bucket based on the priority, wherein the priorityindicates: that logic design flaws corresponding to the logic bucket areto be resolved prior to the integration design flaws or the macro designflaws, that integration design flaws are to be resolved in parallel withmacro design flaws, and that the macro design flaws are to be resolvedprior to the integration design flaws in response to detecting a highslew time, wherein the integration design flaws correspond to a wiredelay issue or a buffer delay issue and, wherein the macro design flawscorrespond to an actual virtual time that exceeds a best case time by athreshold time delay amount. Additionally, detecting, by the one or moreprocessors, a modification to the circuit design based on the logicdesign flaws, the integration design flaws, and the macro design flaws,and applying, by the one or more processors, the modification to thecircuit design to enable manufacturing an integrated circuit, wherein anoverall delay between two latches of the integrated circuit is below apredetermined threshold.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 depicts a block diagram of an example computing system that canmodify a circuit design according to an embodiment described herein;

FIG. 2 is a process flow diagram of an example method that can modify acircuit design according to an embodiment described herein;

FIG. 3 is a process flow diagram for assigning design flaws to a logicbucket, an integration bucket, or a macro bucket;

FIG. 4 is a tangible, non-transitory computer-readable medium that canmodify a circuit design according to an embodiment described herein;

FIG. 5 depicts an illustrative cloud computing environment according toan embodiment described herein;

FIG. 6 depicts a set of functional abstraction layers provided by acloud computing environment according to an embodiment described herein;and

FIG. 7 depicts a block diagram of components of the server computerexecuting the intelligent mapping program within the distributed dataprocessing environment of FIG. 1, in accordance with an embodiment ofthe present invention.

DETAILED DESCRIPTION

Static timing analysis (STA) is a technique for simulating the expectedtiming of a digital circuit without requiring a simulation of the fullcircuit. In some examples, high performance integrated circuits havetraditionally been characterized by the clock frequency at which theintegrated circuits operate. Determining the ability of a circuit tooperate at a specified speed can include measuring, during the designprocess, the delay within the circuit. Moreover, delay calculation canbe incorporated into the inner loop of timing optimizers at variousphases of design, such as logic synthesis, layout (placement androuting), and in in-place optimizations performed late in the designcycle. Static timing analysis enables the fast and reasonably accuratemeasurement of circuit timing.

In some embodiments, the structure and behavior of electronic circuitsand digital logic circuits can be described using a hardware descriptionlanguage (HDL). HDLs enable precise, formal descriptions of electroniccircuits that allow for automated analysis and simulation. For example,the electronic circuits can include complex circuits such asapplication-specific integrated circuits (ASICs), microprocessors, andprogrammable logic devices (PLDs). HDLs are standard text-basedexpressions of the structure of electronic systems and their behaviorover time. HDLs thus also include an explicit notion of time, which canbe a primary attribute of hardware. For example, the Very High SpeedIntegrated Circuit (VHSIC) Hardware Description Language (VHDL) is anHDL used in electronic design automation to describe digital andmixed-signal systems such as field-programmable gate arrays andintegrated circuits. A macro written in VHDL can include multiple designabstractions organized as a hierarchy. For example, a higher level of ahierarchy can be a register-transfer level (RTL). An RTL can be used tomodel a synchronous digital circuit in terms of the flow of digitalsignals (i.e., data) between hardware registers, and the logicaloperations performed on those signals. In some embodiments, lower-levelrepresentations and ultimately actual wiring can be derived from higherlevel representations.

In some embodiments described herein, a device for designing a circuitcan detect negative paths for a circuit design based on a circuit timingtest of the circuit design, in which improves the art by enabling thediagnosis of broken logic in early stages of a project. In someexamples, the slack associated with each path in a circuit is thedifference between the required delay time of an electrical signal usingthe path and the estimated or actual arrival time of an electricalsignal using the path. In various embodiments, a positive slack orpositive path indicates that the arrival time at a gate or node in acircuit can be increased without affecting the overall delay of thecircuit. Conversely, in various embodiments, negative slack implies thata path of a circuit is too slow, and the path can be sped up (or thereference signal delayed) if the whole circuit is to work at a desiredspeed. A path with negative slack is referred to herein as a negativepath.

In some embodiments, the device can also assign each negative path to alogic bucket, an integration bucket, or a macro bucket, wherein thelogic bucket, the integration bucket, and the macro bucket correspond todifferent design flaws such as logic design flaws, integration designflaws, and macro design flaws. Additionally, the device can detect amodification to the circuit design based on the different design flawsand apply the modification to the circuit design to enable manufacturingan integrated circuit, wherein an overall delay between two latches ofthe integrated circuit is below a predetermined threshold, improving theart. Accordingly, the techniques described herein can reduce latency ina circuit or a system on a chip.

With reference now to FIG. 1, an example computing device is depictedthat can modify a circuit. FIG. 1 is a functional block diagramillustrating a distributed data processing environment, generallydesignated 100, in accordance with one embodiment of the presentinvention. The term “distributed” as used in this specificationdescribes a computer system that includes multiple, physically distinctdevices that operate together as a single computer system. FIG. 1provides only an illustration of one implementation and does not implyany limitations with regard to the environments in which differentembodiments can be implemented. Many modifications to the depictedenvironment can be made by those skilled in the art without departingfrom the scope of the invention as recited by the claims.

Computing device 110 can be, for example, a server, desktop computer,laptop computer, tablet computer, or smartphone. In some examples,computing device 110 can be a cloud computing node. Computing device 110can be described in the general context of computer system executableinstructions, such as program modules, being executed by a computersystem. Generally, program modules can include routines, programs,objects, components, logic, data structures, and so on that performparticular tasks or implement particular abstract data types. Computingdevice 110 can be practiced in distributed cloud computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed cloud computingenvironment, program modules can be located in both local and remotecomputer system storage media including memory storage devices. Invarious embodiments, computing device 110 can include and/or beintegrated with the elements of FIG. 7.

Distributed data processing environment 100 includes computing device110 and server computer 120, interconnected over network 130. Network130 can be, for example, a telecommunications network, a local areanetwork (LAN), a wide area network (WAN), such as the Internet, or acombination of the three, and can include wired, wireless, or fiberoptic connections. Network 130 can include one or more wired and/orwireless networks that are capable of receiving and transmitting data,voice, and/or video signals, including multimedia signals that includevoice, data, and video information. In general, network 130 can be anycombination of connections and protocols that will supportcommunications between computing device 110 and server computer 120, andother computing devices (not shown in FIG. 1) within distributed dataprocessing environment 100. In various embodiments, computing device 110can include user interface 106, and/or user interface 106. In otherembodiments, not depicted in FIG. 1, can include a database and/or alocal storage.

In various embodiments, computing device 110 can be, but is not limitedto, a standalone device, a server, a laptop computer, a tablet computer,a netbook computer, a personal computer (PC), a smart phone, a desktopcomputer, a smart television, a smart watch, any programmable electroniccomputing device capable of communicating with various components anddevices within distributed data processing environment 100, via network102 or any combination therein. In general, computing device 110 arerepresentative of any programmable mobile device or a combination ofprogrammable mobile devices capable of executing machine-readableprogram instructions and communicating with users of other mobiledevices via network 130 and or capable of executing machine-readableprogram instructions and communicating with server computer 120. Inother embodiments, computing device 110 can represent any programmableelectronic computing device or combination of programmable electroniccomputing devices capable of executing machine readable programinstructions, manipulating executable machine readable instructions, andcommunicating with server computer 120 and other computing devices (notshown) within distributed data processing environment 100 via a network,such as network 130. Computing device 110 includes an instance of userinterface 106. Computing device 110 and user interface 106 allow a userto interact with modifying circuit component 108 in various ways, suchas sending program instructions, receiving messages, sending data,inputting data, editing data, correcting data and/or receiving data.Server computer 120 may include internal and external hardwarecomponents, as depicted and described in further detail with respect toFIG. 7.

In various embodiments, user interface 106 can provide an interface tomodifying circuit component 108 on server computer 120 for a user ofcomputing device 110. In one embodiment, user interface 106 may be agraphical user interface (GUI) or a web user interface (WUI) and candisplay text, documents, web browser windows, user options, applicationinterfaces, and instructions for operation, and include the information(such as graphic, text, and sound) that a program presents to a user andthe control sequences the user employs to control the program. Inanother embodiment, user interface 106 may also be mobile applicationsoftware that provides an interface between a user of computing device110 and server computer 120. Mobile application software, or an “app,”is a computer program designed to run on smart phones, tablet computersand other mobile devices. In an embodiment, user interface 106 enablesthe user of computing device 110 to send data, input data, edit data,correct data and/or receive data.

Server computer 120 can be a standalone computing device, a managementserver, a web server, a mobile computing device, or any other electronicdevice or computing system capable of receiving, sending, and processingdata. In other embodiments, server computer 120 can represent a servercomputing system utilizing multiple computers as a server system, suchas in a cloud computing environment. In another embodiment, servercomputer 120 can be a laptop computer, a tablet computer, a netbookcomputer, a personal computer (PC), a desktop computer, a personaldigital assistant (PDA), a smart phone, or any other programmableelectronic device capable of communicating with computing device 110 andother computing devices (not shown) within distributed data processingenvironment 100 via network 130. In another embodiment, server computer120 represents a computing system utilizing clustered computers andcomponents (e.g., database server computers, application servercomputers, etc.) that act as a single pool of seamless resources whenaccessed within distributed data processing environment 100. Servercomputer 120 may include internal and external hardware components, asdepicted and described in further detail with respect to FIG. 7.

Database 122 can be a data repository and/or a database that may bewritten to and read by one or a combination of server computer 120and/or computing device 110. In the depicted embodiment, database 122resides on server computer 120. In another embodiment, database 122 mayreside elsewhere within distributed data processing environment 100modifying circuit component 108 has access to database 122. A databaseis an organized collection of data. Database 122 can be implemented withany type of storage device capable of storing data and configurationfiles that can be accessed and utilized by server computer 120, such asa database server, a hard disk drive, or a flash memory. Database 122stores coverage data of a user. In other embodiments, database 122 canbe hard drives, memory cards, computer output to laser disc (coldstorage), and or any form of data storage known in the art.

In the exemplary embodiment, modifying circuit component 108 is housedon computing device 110; however, in other embodiments, modifyingcircuit component 108 can be housed on server computer 120, network 130,and/or another computing device not shown in environment 100. In variousembodiments, modifying circuit component 108 can include subcomponentspath manager 112, bucket manager 114, and/or circuit modifier 116. Insome embodiments, path manager 112 can detect negative paths for acircuit design based on a circuit timing test of the circuit design. Insome embodiments, bucket manager 114 can assign each negative path to alogic bucket, an integration bucket, and/or a macro bucket, wherein thelogic bucket corresponds to logic design flaws, the integration bucketcorresponds to integration design flaws, and the macro bucketcorresponds to macro design flaws or design flaws residing within amacro of the circuit design. In some embodiments, circuit modifier 116can detect a modification to the circuit design based on the logicdesign flaws, the integration design flaws, and the macro design flaws.Circuit modifier 116 can also apply the modification to the circuitdesign to enable manufacturing an integrated circuit, wherein an overalldelay between two latches of the integrated circuit is below apredetermined threshold.

It is to be understood that the block diagram of FIG. 1 is not intendedto indicate that computing device 110 is to include all of thecomponents shown in FIG. 1. Rather, computing device 110 can includefewer or additional components not illustrated in FIG. 1 (e.g.,additional memory components, embedded controllers, modules, additionalnetwork interfaces, etc.). Furthermore, any of the functionalities ofpath manager 112, bucket manager 114, and circuit modifier 116 can bepartially, or entirely, implemented in hardware and/or in theprocessors. For example, the functionality can be implemented with anapplication specific integrated circuit, logic implemented in anembedded controller, or in logic implemented in the processors, amongothers. In some embodiments, the functionalities of path manager 112,bucket manager 114, and circuit modifier 116 can be implemented withlogic, wherein the logic, as referred to herein, can include anysuitable hardware (e.g., a processor, among others), software (e.g., anapplication, among others), firmware, or any suitable combination ofhardware, software, and firmware.

FIG. 2 is a process flow diagram of an example method that can modify acircuit. The method 200 can be implemented with any suitable computingdevice, such as computing device 110 of FIG. 1. FIG. 2 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be madeby those skilled in the art without departing from the scope of theinvention as recited by the claims.

At step 202, path manager 112 can detect negative paths for a circuitdesign based on a circuit timing test of the circuit design. Forexample, as discussed above, the slack associated with each path in acircuit can be measured as the difference between the required range oftime for the path to transmit an electrical signal and the estimatedarrival time of an electrical signal using the path. In some examples,the estimated arrival time is based on a simulation or circuit timingtest of the circuit. A positive slack implies that the arrival time at agate or node in the circuit can be increased without affecting theoverall delay of the circuit. Conversely, negative slack implies that apath is too slow, and the path can be sped up (or the reference signaldelayed) if the whole circuit is to work at a desired speed. A path withnegative slack is referred to herein as a negative path. In someexamples, path manager 112 can store the negative paths for a circuit inany suitable abstract data type, database, or file, among others. Pathmanager 112 can also group negative paths based on macros or regionswithin a circuit. A macro, as referred to herein, can include asub-division of a circuit based on related logic that performs a commontask. For example, a macro can include logic performing an addercalculation, or logic performing address generation, among others. Insome examples, path manager 112 can group negative paths locatedproximate one another into a first set and negative paths located morethan a predetermined distance from the first set can be stored as asecond set. In some embodiments, path manager 112 can use circuit timingtests that identify negative paths in any suitable number of regions ormacros of an integrated circuit, which can be a processor, a system on achip, and the like.

At step 204, bucket manager 114 can assign each negative path to a logicbucket, an integration bucket, or a macro bucket, wherein the logicbucket, the integration bucket, and the macro bucket correspond to macrodesign flaws or design flaws residing within a macro of the circuit. Alogic bucket, as referred to herein, can indicate a logic design flaw ina circuit corresponding to gate delay times exceeding a cycle time forthe circuit or gate delays in addition to an optimal integration delayexceeding a cycle time for the circuit. An integration bucket, asreferred to herein, can indicate macro design flaws such as macros beingtoo far apart, and wire delay issues, among other integration designflaws. In some examples, the integration bucket indicates integrationdesign flaws based on a Manhattan distance of two gates in a circuit. Amacro bucket, as referred to herein, can indicate macro design flawswithin a single macro such as wires that exceed a necessary length,buffers that exceed a necessary size, and the like. In some examples,the macro bucket can indicate macro design flaws corresponding toadders, dividers, and the like. For example, the macro bucket canindicate macro design flaws corresponding to multiple gates within amacro of a circuit design. In some embodiments, a macro bucket canindicate that a ratio of a best case delay time to an actual orestimated delay time exceeds a predetermined ratio. In some examples,the macro design flaw corresponds to an actual virtual time that exceedsa best case time by a threshold time delay amount.

In some embodiments, bucket manager 114 can indicate a logic design flawbased on a zero wire length tool that eliminates wire delay. The zerowire length tool can isolate logic delay associated with gates andlatches to provide a best case time for a macro without a wire delay. Invarious embodiments, a latch, as referred to herein, includes a circuitwith two stable states that can be used to store state information. Insome examples, bucket manager 114 can include the wire delay if macrosbeing analyzed are located in different partitions of an integratedcircuit or processing core. In some embodiments, bucket manager 114 candetect a priority of logic design flaws in the logic bucket,integrations design flaws in the integration bucket, and macro designflaws in the macro bucket, and assign each negative path to the logicbucket, the integration bucket, and the macro bucket based on thepriority. The prioritization of design flaws is discussed below inrelation to step 206.

At step 206, circuit modifier 116 can detect a modification to thecircuit design based on the different design flaw. In some embodiments,circuit modifier 116 can detect modifications to multiple aspects of acircuit and detect a priority for each of the design flaws. For example,circuit modifier 116 can detect design flaws in a logic bucket, anintegration bucket, and a macro bucket, or any combination thereof.Circuit modifier 116 can apply modifications to the circuit to preventlogic design flaws prior to applying modifications to the circuit toprevent integration or macro design flaws. In some examples, circuitmodifier 116 can also apply a modification to correct for an integrationdesign flaw in parallel with correcting a macro design flaw. Although,circuit modifier 116 can apply a modification to correct a macro designflaw prior to correcting an integration design flaw if a high slew timeof a path is above a predetermined slew threshold.

At step 208, circuit modifier 116 can apply the modification to thecircuit design to enable manufacturing an integrated circuit, wherein anoverall delay between two latches of the integrated circuit is below apredetermined threshold. For example, circuit modifier 116 can modify asimulation of a circuit or a manufacturing of a circuit based on theidentified modifications that correct for logic design flaws, macrodesign flaws, and integration design flaws. In some embodiments, circuitmodifier 116 can transmit instructions to an automated manufacturingdevice to manufacture a circuit with fewer negative paths, which canreduce latency in the circuit.

The process flow diagram of FIG. 2 is not intended to indicate that theoperations of the method 200 are to be executed in any particular order,or that all of the operations of the method 200 are to be included inevery case. For example, bucket manager 114 can detect any number ofnegative paths for a circuit and process the negative paths in anysuitable order.

FIG. 3 is a process flow diagram of an example method that can assigndesign flaws to a logic bucket, an integration bucket, or a macrobucket. The method 300 can be implemented with any suitable computingdevice, such as computing device 110 of FIG. 1. FIG. 3 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be madeby those skilled in the art without departing from the scope of theinvention as recited by the claims.

At step 302, path manager 112 can detect a timing report. In someembodiments, the timing report can indicate timing delays for any numberof paths in an integrated circuit design. In some examples, the timingreport can be provided by a remote device to a cloud service thatexecutes path manager 112. In other embodiments, path manager 112 candetect the timing report on a local computing device. In some examples,the timing report can indicate an estimated time to transmit anelectrical signal within a macro, or between multiple macros andmultiple gates, among others.

At step 304, bucket manager can detect if the gate delay for a negativepath, in addition to an optimal integration delay, is less than a cycletime. The optimal integration delay can indicate a best case amount ofdelay to transmit an electrical signal between two macros of a circuit.If so, the process continues at steps 306 and 308.

At step 306, bucket manager can detect a macro design flaw in thenegative path. For example, the macro design flaw can indicate delays inwires, assertions, pinning, and placement of a macro in a circuit. Insome embodiments, the macro design flaw can indicate than an output pinof a macro is in a location that increases the amount of time totransmit an electrical signal beyond a threshold value. The macro designflaw can also indicate that a path inside of a macro has a weak gatewith a small number of transistors corresponding to a high load.Accordingly, the macro design flaw can indicate that the amount of timefor the weak gate with a small number of transistors to transmit asignal exceeds a threshold value.

At step 310, bucket manager can assign the macro design flaw to a macrobucket. In some examples, the macro bucket can indicate a group ofusers, software tools, and the like, which can correct the macro designflaw. For example, the macro bucket can indicate that a stronger gatewith additional transistors is needed in a macro to process a high load.Accordingly, a macro can be redesigned with additional transistors toprocess a high load electrical signal.

At step 308, bucket manager can detect an integration design flaw. Forexample, the integration design flaw can correspond to a distanceassociated with two gates or latches, among other integration designflaws. In some embodiments, the integration design flaw can indicate abuffer delay issue in which a repeater is too weak to transmit anelectrical signal across a distance between two gates or latches. Insome examples, the integration design flaw can also indicate that anelectrical signal is to be transmitted via a wire at a higher level toincrease the speed at which the electrical signal is transmitted betweentwo gates or latches.

At step 312, bucket manager can assign the integration design flaw to anintegration bucket. In some embodiments, the integration bucket canindicate a group of users or software tools that can correct theintegration design flaw. For example, the integration bucket canindicate that a low power repeater is to be replaced with a high powerrepeater, or an electrical signal is to be transmitted through adifferent wire at a higher level, among others.

Returning to step 302, the process can continue at step 314 by detectingthat a gate delay of a negative path is greater than a cycle time orthat a gate delay of a negative path in a macro plus an optimalintegration delay is greater than a cycle time. The gate delay exceedingthe cycle time can indicate a logic design flaw as described above. Forexample, the logic design flaw can indicate that a sum delay for gatesbetween two latches exceeds a cycle time or a cycle time threshold. Insome examples, a circuit can include a driving latch that transmits anelectrical signal to a receiving latch. The circuit can include anynumber of NAND gates, XOR gates, NOR gates, OR gates, among other gates,between the driving latch and the receiving latch. In some embodiments,the logic design flaw can indicate that the sum delay of the gatesbetween the driving latch and the receiving latch exceeds a cycle time.

At step 316, bucket manager can assign the logic design flaw to a logicbucket. In some embodiments, the logic bucket can indicate a group ofusers or software tools that can correct the logic design flaw. Forexample, the logic bucket can indicate that a circuit is to includefewer gates between two latches, or that different gates are to beincluded between two latches, among others. In some embodiments, thelogic design flaw can be tested iteratively by removing a single gatebetween two latches and determining if the gate delay is still greaterthan a cycle time of the circuit. The testing can be repeated until thenumber of gates between two latches results in transmission of anelectrical signal with a delay less than a cycle time of the circuit.

The process flow diagram of FIG. 3 is not intended to indicate that theoperations of the method 300 are to be executed in any particular order,or that all of the operations of the method 300 are to be included inevery case. In some embodiments, bucket manager can execute steps 304and 314 simultaneously to identify logic design flaws and macro designflaws or integration design flaws in parallel. In some embodiments,circuit design specialists or machine learning techniques can be used todetect the macro design flaws, integration design flaws, and logicdesign flaws.

The present invention can be a system, a method, and/or a computerprogram product. The computer program product can include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium can be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network can comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention can be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions can execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer can be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection can be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) can execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions can be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionscan also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions can also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams can represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical functions. In some alternativeimplementations, the functions noted in the block can occur out of theorder noted in the figures. For example, two blocks shown in successioncan, in fact, be executed substantially concurrently, or the blocks cansometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Referring now to FIG. 4, a block diagram is depicted of an example of atangible, non-transitory computer-readable medium that can modify acircuit design. The tangible, non-transitory, computer-readable medium400 can be accessed by a processor 402 over a computer interconnect 404.FIG. 2 provides only an illustration of one implementation and does notimply any limitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironment may be made by those skilled in the art without departingfrom the scope of the invention as recited by the claims.

Furthermore, the tangible, non-transitory, computer-readable medium 400can include code to direct the processor 402 to perform the operationsof the current method, and house modifying circuit component 108, andmodifying circuit component 108 subcomponents. In the exemplaryembodiment, modifying circuit component 108 subcomponents are housed oncomputer-readable medium 400. For example, path manager 112 can detectnegative paths for a circuit design based on a circuit timing test ofthe circuit design. In some embodiments, bucket manager 114 can assigneach negative path to a logic bucket, an integration bucket, or a macrobucket, wherein the logic bucket corresponds to logic design flaws, theintegration bucket corresponds to integration design flaws, and themacro bucket corresponds to macro design flaws or design flaws residingwithin a macro of the circuit design. In some embodiments, circuitmodifier 116 can detect a modification to the circuit design based onthe logic design flaws, the integration design flaws, and the macrodesign flaws. Circuit modifier 116 can also apply the modification tothe circuit design to enable manufacturing an integrated circuit,wherein an overall delay between two latches of the integrated circuitis below a predetermined threshold.

It is to be understood that any number of additional software componentsnot shown in FIG. 4 can be included within the tangible, non-transitory,computer-readable medium 400, depending on the specific application.Furthermore, fewer software components than those shown in FIG. 4 can beincluded in the tangible, non-transitory, computer-readable medium 400.

Referring now to FIG. 5, illustrative cloud computing environment 500 isdepicted. As shown, cloud computing environment 500 comprises one ormore cloud computing nodes 502 with which local computing devices usedby cloud consumers, such as, for example, personal digital assistant(PDA) or cellular telephone 504A, desktop computer 504B, laptop computer504C, and/or automobile computer system 504N can communicate. Nodes 502can communicate with one another. They can be grouped (not shown)physically or virtually, in one or more networks, such as Private,Community, Public, or Hybrid clouds as described hereinabove, or acombination thereof. This allows cloud computing environment 500 tooffer infrastructure, platforms and/or software as services for which acloud consumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 504A-Nshown in FIG. 5 are intended to be illustrative only and that computingnodes 502 and cloud computing environment 500 can communicate with anytype of computerized device over any type of network and/or networkaddressable connection (e.g., using a web browser).

Referring now to FIG. 6, a set of functional abstraction layers providedby cloud computing environment 500 (FIG. 5) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 6 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided.

Hardware and software layer 600 includes hardware and softwarecomponents. Examples of hardware components include mainframes 601, inone example IBM® zSeries® systems; RISC (Reduced Instruction SetComputer) architecture based servers 603, in one example IBM pSeries®systems; servers 605, in one example IBM xSeries® systems; blade servers607, in one example IBM BladeCenter® systems; storage devices 609;networks and networking components 611. Examples of software componentsinclude network application server software 613, in one example IBMWebSphere® application server software; and database software 615, inone example IBM DB2® database software. (IBM, zSeries, pSeries, xSeries,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide).

Virtualization layer 602 provides an abstraction layer from which thefollowing examples of virtual entities can be provided: virtual servers617; virtual storage 619; virtual networks 621, including virtualprivate networks; virtual applications and operating systems 623; andvirtual clients 625.

In one example, management layer 604 can provide the functions describedbelow. Resource provisioning 627 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 629provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources can comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 631 provides access to the cloud computing environment forconsumers and system administrators. Service level management 633provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 635 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 606 provides examples of functionality for which thecloud computing environment can be utilized. Examples of workloads andfunctions which can be provided from this layer include: mapping andnavigation 631; software development and lifecycle management 633;virtual classroom education delivery 635; data analytics processing 637;transaction processing 639; and modifying circuit component 108 based ondesign flaws in a logic bucket, macro bucket, or integration bucket. Invarious embodiments, modifying circuit component 108 can includemodifying subcomponents path manager 112, bucket manager 114, and/orcircuit modifier 116.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

FIG. 7 depicts a block diagram of components of a computing devicewithin distributed data processing environment 100 of FIG. 1, inaccordance with an embodiment of the present invention. It should beappreciated that FIG. 7 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments can be implemented. Manymodifications to the depicted environment can be made.

FIG. 7 depicts computer system 700, where server computer 120 representsan example of computer system 700 that includes cognitive health andnutrition advisor. The computer system includes processors 701, cache703, memory 702, persistent storage 705, communications unit 707,input/output (I/O) interface(s) 706 and communications fabric 704.Communications fabric 704 provides communications between cache 703,memory 702, persistent storage 705, communications unit 707, andinput/output (I/O) interface(s) 706. Communications fabric 704 can beimplemented with any architecture designed for passing data and/orcontrol information between processors (such as microprocessors,communications and network processors, etc.), system memory, peripheraldevices, and any other hardware components within a system. For example,communications fabric 704 can be implemented with one or more buses or acrossbar switch.

Memory 702 and persistent storage 705 are computer readable storagemedia. In this embodiment, memory 702 includes random access memory(RAM). In general, memory 702 can include any suitable volatile ornon-volatile computer readable storage media. Cache 703 is a fast memorythat enhances the performance of processors 701 by holding recentlyaccessed data, and data near recently accessed data, from memory 702.

Program instructions and data used to practice embodiments of thepresent invention may be stored in persistent storage 705 and in memory702 for execution by one or more of the respective processors 701 viacache 703. In an embodiment, persistent storage 705 includes a magnetichard disk drive. Alternatively, or in addition to a magnetic hard diskdrive, persistent storage 705 can include a solid state hard drive, asemiconductor storage device, read-only memory (ROM), erasableprogrammable read-only memory (EPROM), flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 705 may also be removable. Forexample, a removable hard drive may be used for persistent storage 705.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage705.

Communications unit 707, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 707 includes one or more network interface cards.Communications unit 707 may provide communications through the use ofeither or both physical and wireless communications links. Programinstructions and data used to practice embodiments of the presentinvention may be downloaded to persistent storage 705 throughcommunications unit 707.

I/O interface(s) 706 enables for input and output of data with otherdevices that may be connected to each computer system. For example, I/Ointerface 706 may provide a connection to external devices 708 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 708 can also include portable computer readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data used to practiceembodiments of the present invention can be stored on such portablecomputer readable storage media and can be loaded onto persistentstorage 705 via I/O interface(s) 706. I/O interface(s) 706 also connectto display 709.

Display 709 provides a mechanism to display data to a user and may be,for example, a computer monitor.

What is claimed is:
 1. A method for modifying circuits to optimize thetime required to diagnose broken logic, the method comprising:detecting, by one or more processors, negative paths for a circuitdesign based on a circuit timing test of the circuit design, wherein thedetection of negatives paths enables the diagnosis of broken logic inearly stages of a project; assigning, by the one or more processors,each negative path to a logic bucket, an integration bucket, or a macrobucket, wherein the logic bucket corresponds to logic design flaws, theintegration bucket corresponds to integration design flaws, and themacro bucket corresponds to macro design flaws or design flaws residingwithin a macro of the circuit design; detecting, by one or moreprocessors, a priority of the logic design flaws, the integration designflaws, and the macro design flaws; and assigning each negative path tothe logic bucket, the integration bucket, and the macro bucket based onthe priority, wherein the priority indicates: that logic design flawscorresponding to the logic bucket are to be resolved prior to theintegration design flaws or the macro design flaws, that integrationdesign flaws are to be resolved in parallel with macro design flaws, andthat the macro design flaws are to be resolved prior to the integrationdesign flaws in response to detecting a high slew time, wherein theintegration design flaws correspond to a wire delay issue or a bufferdelay issue and, wherein the macro design flaws correspond to an actualvirtual time that exceeds a best case time by a threshold time delayamount; detecting, by the one or more processors, a modification to thecircuit design based on the logic design flaws, the integration designflaws, and the macro design flaws; applying, by the one or moreprocessors, the modification to the circuit design to enablemanufacturing of an integrated circuit and to correct the integrationdesign flaws in parallel with the macro design flaws based on thedetected priority of the logic design flaws, the integration designflaws, and the macro design flaws, wherein an overall delay between twolatches of the integrated circuit is below a predetermined threshold,and transmit instructions to an automated manufacturing device tomanufacture a circuit with fewer negative paths to reduce latency in thecircuit.